(Rmail Coding) <rmail-redecode-body>: Remove stale documentation of

possible problems with redecoding.

diff --git a/doc/emacs/rmail.texi b/doc/emacs/rmail.texi
index 844fa34cb4e52a9c8b6ef6b7439a36d059c662f8..1d07f1cc2c146d1c5ad47e54f99d2da891249a5d 100644 (file)
--- a/doc/emacs/rmail.texi
+++ b/doc/emacs/rmail.texi
@@ -1098,24 +1098,10 @@ its characters displayed as empty boxes, this may have happened.
   You can correct the problem by decoding the message again using the
 right coding system, if you can figure out or guess which one is
 right.  To do this, invoke the @kbd{M-x rmail-redecode-body} command.
-It reads the name of a coding system, encodes the message body using
-whichever coding system was used to decode it before, then redecodes
-it using the coding system you specified.  If you specified the right
+It reads the name of a coding system, and then redecodes the message
+using the coding system you specified.  If you specified the right
 coding system, the result should be readable.
 
-  Decoding and encoding using the wrong coding system is lossless for
-most encodings, in particular with 8-bit encodings such as iso-8859 or
-koi8.  So, if the initial attempt to redecode the message didn't
-result in a legible text, you can try other coding systems until you
-succeed.
-
-  With some coding systems, notably those from the iso-2022 family,
-information can be lost in decoding, so that encoding the message
-again won't bring back the original incoming text.  In such a case,
-@code{rmail-redecode-body} cannot work.  However, the problems that
-call for use of @code{rmail-redecode-body} rarely occur with those
-coding systems.  So in practice the command works when you need it.
-
 @node Rmail Editing
 @section Editing Within a Message